Assignable TemplateLiteral of Intersection Type of Primitive and {} to Primitive String#61174
Closed
horita-yuya wants to merge 1 commit intomicrosoft:mainfrom
Closed
Assignable TemplateLiteral of Intersection Type of Primitive and {} to Primitive String#61174horita-yuya wants to merge 1 commit intomicrosoft:mainfrom
horita-yuya wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Author
|
@microsoft-github-policy-service agree |
horita-yuya
changed the title
horita-yuya
changed the title
Collaborator
|
With 6.0 out as the final release vehicle for this codebase, we're closing all PRs that don't fit the merge criteria for post-6.0 patches. If you think this was a mistake and this PR fits the post-6.0 patch criteria, please post to the 6.0 iteration issue with details (specifically, which PR and which patch criteria it satisfies). Next steps for PRs:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #60990 (partially)
We can use a technique called branded types by defining a type as
primitive & { brand: "branded" }.This has the benefit of allowing you to handle the target primitive type more constrainedly. For example, with
1 & { brand: "branded" }type, it can only be used in a narrower context than the literal type1.The relationship between the types is:
In other words,
1 & { brand: "branded" }can be assigned to a1type, and1can be assigned to anumbertype.Wouldn't it be more natural to handle Template Literals similarly?